Skip to content

Conversation

@fallmo
Copy link
Contributor

@fallmo fallmo commented Nov 1, 2025

Untitled

Safari does not properly constrain images using max-height: 100% when the parent element has a fixed max-height. As a result, the custom masthead logo ignores the intended 60 px limit on Safari.

This change explicitly applies max-height: 60px to the child img element to ensure consistent behavior across browsers.

Explicitly set max-height for browser compatibility (safari)

Signed-off-by: Mohamed Fall <[email protected]>
@openshift-ci openshift-ci bot requested review from rhamilto and sg00dwin November 1, 2025 13:39
@openshift-ci openshift-ci bot added component/core Related to console core functionality needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 1, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 1, 2025

Hi @fallmo. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@rhamilto
Copy link
Member

rhamilto commented Nov 5, 2025

/assign @sg00dwin

Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 5, 2025
@fallmo
Copy link
Contributor Author

fallmo commented Nov 7, 2025

/retest-required

Copy link
Member

@sg00dwin sg00dwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 7, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fallmo, logonoff, sg00dwin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@logonoff
Copy link
Member

logonoff commented Nov 7, 2025

/retitle NO-JIRA: Fix logo max-height not respected on Safari
/label px-approved
/label docs-approved

qe review:
/assign @yapei

@openshift-ci openshift-ci bot changed the title Fix logo max-height not respected on Safari NO-JIRA: Fix logo max-height not respected on Safari Nov 7, 2025
@openshift-ci openshift-ci bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Nov 7, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 7, 2025
@openshift-ci-robot
Copy link
Contributor

@fallmo: This pull request explicitly references no jira issue.

In response to this:

Untitled

Safari does not properly constrain images using max-height: 100% when the parent element has a fixed max-height. As a result, the custom masthead logo ignores the intended 60 px limit on Safari.

This change explicitly applies max-height: 60px to the child img element to ensure consistent behavior across browsers.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@yapei
Copy link
Contributor

yapei commented Nov 11, 2025

  1. Create a ConfigMap from logo file in which the height is more than 60px
oc create cm custom-logos-config --from-file=/Users/yapei/Desktop/personal-pic.jpeg -n openshift-config
configmap/custom-logos-config created
  1. Update console to use custom logo
oc get console.operator cluster -o json | jq .spec.customization.logos
[
  {
    "themes": [
      {
        "mode": "Light",
        "source": {
          "configMap": {
            "key": "personal-pic.jpeg",
            "name": "custom-logos-config"
          },
          "from": "ConfigMap"
        }
      }
    ],
    "type": "Masthead"
  }
]
  1. Check logo in different browsers

reproduced the issue on 420 cluster, also confirmed that Safari now respect max-height as other browsers(Chrome, Firefox and Edge)
Safari

/verified by @yapei

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 11, 2025
@openshift-ci-robot
Copy link
Contributor

@yapei: This PR has been marked as verified by @yapei.

In response to this:

  1. Create a ConfigMap from logo file in which the height is more than 60px
oc create cm custom-logos-config --from-file=/Users/yapei/Desktop/personal-pic.jpeg -n openshift-config
configmap/custom-logos-config created
  1. Update console to use custom logo
oc get console.operator cluster -o json | jq .spec.customization.logos
[
 {
   "themes": [
     {
       "mode": "Light",
       "source": {
         "configMap": {
           "key": "personal-pic.jpeg",
           "name": "custom-logos-config"
         },
         "from": "ConfigMap"
       }
     }
   ],
   "type": "Masthead"
 }
]
  1. Check logo in different browsers

reproduced the issue on 420 cluster, also confirmed that Safari now respect max-height as other browsers(Chrome, Firefox and Edge)
Safari

/verified by @yapei

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sg00dwin sg00dwin changed the title NO-JIRA: Fix logo max-height not respected on Safari OCPBUGS-64939: Fix logo max-height not respected on Safari Nov 11, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 11, 2025
@openshift-ci-robot
Copy link
Contributor

@fallmo: This pull request references Jira Issue OCPBUGS-64939, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Untitled

Safari does not properly constrain images using max-height: 100% when the parent element has a fixed max-height. As a result, the custom masthead logo ignores the intended 60 px limit on Safari.

This change explicitly applies max-height: 60px to the child img element to ensure consistent behavior across browsers.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from yapei November 11, 2025 14:26
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fb56d17 and 2 for PR HEAD badb1fb in total

@openshift-merge-bot openshift-merge-bot bot merged commit 41e0ca6 into openshift:main Nov 12, 2025
7 of 8 checks passed
@openshift-ci-robot
Copy link
Contributor

@fallmo: Jira Issue Verification Checks: Jira Issue OCPBUGS-64939
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-64939 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

Untitled

Safari does not properly constrain images using max-height: 100% when the parent element has a fixed max-height. As a result, the custom masthead logo ignores the intended 60 px limit on Safari.

This change explicitly applies max-height: 60px to the child img element to ensure consistent behavior across browsers.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-11-13-042845

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality docs-approved Signifies that Docs has signed off on this PR jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. px-approved Signifies that Product Support has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants